Sealing introduction
Introduction to Sealing as a Service (SaaS) in the Filecoin Ecosystem
Sealing as a Service (SaaS) represents a transformative approach in the Filecoin network. It offers storage providers the option to delegate the sealing process to specialized sealers, enhancing overall efficiency, flexibility, and scalability. As the Filecoin ecosystem continues to evolve, so too does the implementation and refinement of SaaS, and we're at the forefront of its optimization alongside the broader community.
In this chapter, readers can expect:
- A comprehensive understanding of what Sealing as a Service (SaaS) entails.
- A step-by-step guide on initiating the sealing of sectors.
- Insight into the role and function of sealing workers within the process.
Understanding the Multiple Parties in Sealing as a Service
In the Filecoin Sealing as a Service (Saas) model, there are two key roles: sealers, who perform the computationally intensive sealing tasks, and storage providers, who store the data on the Filecoin network.
In the classic Filecoin model (before sealing as a service is introduced), participants in the Filecoin network were known as miners, who took on the responsibility of both storing the data and preparing it for onboarding to the chain through the sealing process. This was the sole role in the original Filecoin ecosystem.
However, the new model introduces two separate roles: sealers and storage providers. This change brings increased efficiency and scalability in the Filecoin ecosystem. In the SaaS model, storage providers (SPs) can outsource the sealing process to independent sealing providers(compute providers doing data sealing), who specialize in performing the computationally intensive tasks associated with sealing. This division of responsibilities allows each party to focus on their respective tasks, leading to a more robust and efficient network overall.
For those interested in becoming a sealer, it's not necessary to fully understand the intricacies of Filecoin. Sealers can view the sealing process as a "proof of work" (PoW) operation. By participating in this PoW, sealers can earn tokens in exchange for their computing power.
Rest of this chapter will focus on Sealer(compute provider) role in SAAS. If you are interested in providing storage, read intro on Storage providers.
Quickstart
Sealing as a Service (SaaS) Flow
The process of Sealing as a Service (SaaS) is usualy initiated by the storage provider (SP). It is the SP that identifies the need to seal a sector, and in response, creates specific sealing jobs. These jobs act as blueprints detailing the sealing procedure and carry essential information related to the Filecoin sector in question. This includes attributes such as the storage provider id, sector number, is it the CC sector or data should be included from the start, and the ticket required to seal the sector.
Sealers continuously monitor for incoming sealing jobs, processing each promptly as it is received.
Point-to-Point Sealing
In some scenarios, a Sealer may opt to collaborate exclusively with a single storage provider, establishing a direct communication link. This approach is termed as "point-to-point sealing" given that the sole participants in the process are the Sealer and the Storage provider. Such arrangements can be customized according to the mutual needs of the two entities. Payment channels and conditions, for instance, are subject to direct negotiation and agreement.
Compute Marketplace Sealing
An alternative to the point-to-point setup is for sealers to partake in a compute marketplace. This marketplace acts as a reservoir of sealing jobs sourced from various storage providers. The sheer volume and diversity of jobs in such a setup allow for more refined orchestration and specialization. Sealing entities can focus on specific job types that best align with their expertise and capabilities, usually resulting in improved throughput and higher returns.
To successfully process sealing jobs, a Sealer must operate a sealing worker, a topic that will be further elaborated on in subsequent documentation chapters. The sealing process itself is computationally intensive, and as such, it is usually performed on a dedicated machine. The sealing worker is the software responsible for executing the sealing jobs.
Additionally, for enhanced orchestration and to facilitate jobs from multiple sources, a Sealer may opt to run a local job server. Some storage providers may insist on this, as it fosters better management of workflows. Running a job server streamlines the sealing process, ensuring a smoother execution and facilitating troubleshooting, should any issues arise.
How does it work?
Interested in how does the sealing-as-a-service works under the hood? There is a dedicated chapter about that!
How to start?
In order to participate as a sealer in Filecon Sealing as a service, sealer will need to setup a sealing software from web3mine. This chapter guides sealers through setup process.
To begin your journey as a sealer in the Sealing as a Service (SAAS) model, you'll need to install some additional software to complete the sealing jobs. You will need:
- a sealing worker instance (required)
- a job server (recommended)
Continue reading to learn more about these components and how to set them up.
Sealing as a service components:
Sealing as a service is implemented in a modular way and multiple deployment scenarios are possible. For purposes of this tutorial we will assume a simple setup that will consist of:
- one storage provider
- one monolith sealing provider
- a job market
This setup can be seen in the following diagram:
In the SAAS architecture, Storage Providers and Sealers are decoupled. Compute proivders (Sealers) will run only software neccecary to finish sealing jobs.
As a sealer, you will need to run:
- one or more Sealing Worker instances.
- a Job server (optional)
Please note that there are multiple implementations of Sealing workers. We will help you choose one of the implementations in the following sections.
Setting up your sealer
Setting up Sealing worker(s)
You may spin up one or multiple Sealing workers that will execute actual sealing jobs. Sealing workers are daemon processes that execute specific jobs assigned to you.
To learn more about Sealing workers, visit Sealing workers introduction page.
Setting up Job server
You will need to setup a Job server in order to run remote Sealing jobs. Visit Jobs server setup instuctions for more info.
Notes on utilizing the Job Market
Utilizing the Job Market, although optional, is highly recommended for compute providers. It presents an avenue for potentially increased earnings through access to a variety of jobs. What makes the market particularly appealing is its facilitation of specialization. Sealers can choose to focus and optimize on specific job types that align best with their hardware capabilities. For instance, if a sealer's setup boasts a powerful GPU and an abundance of RAM, they might find it more profitable to concentrate solely on C2 job types. This targeted approach can effectively maximize their earnings and optimize the use of their resources.